User plane function (upf) load balancing based on central processing unit (cpu) and memory utilization of the user equipment (ue) in the upf

ABSTRACT

Embodiments are directed towards embodiments are directed toward systems and methods for user plane function (UPF) and network slice load balancing within a 5G network. Example embodiments include systems and methods for load balancing based on current UPF load and thresholds that depend on UPF capacity; UPF load balancing using predicted throughput of new UE on the network based on network data analytics; UPF load balancing based on special considerations for low latency traffic; UPF load balancing supporting multiple slices, maintaining several load-thresholds for each UPF and each slice depending on the UPF and network slice capacity; and UPF load balancing using predicted central processing unit (CPU) utilization and/or predicted memory utilization of new UE on the network based on network data analytics.

TECHNICAL FIELD

The present disclosure relates generally to digital messagecommunications and, more particularly, to user plane function (UPF) loadbalancing within a Fifth Generation (5G) communications network.

BRIEF SUMMARY

As the use of smart phones and Internet of Things (IoT) devices hasincreased, so too has the desire for more reliable, fast, and continuoustransmission of content. In an effort to improve the contenttransmission, networks continue to improve with faster speeds andincreased bandwidth. The advent and implementation of 5G technology hasresulted in faster speeds and increased bandwidth, but with the drawbackof potentially overloading certain portions of the network in certaincircumstances. It is with respect to these and other considerations thatthe embodiments described herein have been made.

5G Core (5GC) is the heart of a 5G mobile network. It establishesreliable, secure connectivity to the network for end users and providesaccess to its services. The core domain handles a wide variety ofessential functions in the mobile network, such as connectivity of newuser equipment (UE) and mobility management, authentication andauthorization, subscriber data management and policy management, amongothers. 5G Core network functions are completely software-based anddesigned as cloud-native, meaning that they're agnostic to theunderlying cloud infrastructure, allowing higher deployment agility andflexibility. With the advent of 5G, industry experts defined how thecore network should evolve to support the needs of 5G New Radio (NR) andthe advanced use cases enabled by it. Together, they developed the 3rdGeneration Partnership Project (3GPP) standard for core networks knownas 5G Core (5GC).

The 5GC architecture is based on what is called a Service-BasedArchitecture (SBA), which implements IT network principles and acloud-native design approach. In this architecture, each networkfunction (NF) offers one or more services to other NFs via ApplicationProgramming Interfaces (API). Each NF, such as the user plane function(UPF) and the Session Management Function (SMF) is formed by acombination of small pieces of software code called as microservices.Some microservices can even be re-used for different NFs, makingimplementation more effective and facilitating independent life-cyclemanagement—which allows upgrades and new functionalities to be deployedwith zero impact on running services.

Briefly described, embodiments are directed toward systems and methodsfor user plane function (UPF) and network slice load balancing within a5G network. Example embodiments include: systems and methods for loadbalancing based on current UPF load and thresholds that depend on UPFcapacity; systems and methods for UPF load balancing using predictedthroughput of new UE on the network based on network data analytics;systems and methods for UPF load balancing based on specialconsiderations for low latency traffic; systems and methods for UPF loadbalancing supporting multiple slices, maintaining severalload-thresholds for each UPF and each slice depending on the UPF andnetwork slice capacity; and systems and methods for UPF load balancingusing predicted central processing unit (CPU) utilization and/orpredicted memory utilization of new UE on the network based on networkdata analytics.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments are described with referenceto the following drawings. In the drawings, like reference numeralsrefer to like parts throughout the various figures unless otherwisespecified.

For a better understanding of the present invention, reference will bemade to the following Detailed Description, which is to be read inassociation with the accompanying drawings:

FIG. 1 illustrates a context diagram of an environment in which UPF loadbalancing may be implemented in accordance with embodiments describedherein;

FIG. 2 illustrates a logical flow diagram showing one embodiment of aprocess for load balancing based on current UPF load and thresholds thatdepend on UPF capacity in accordance with embodiments described herein;

FIG. 3 illustrates a logical flow diagram showing one embodiment of aprocess for selecting the UPF based on generated weights, which isuseful in the process of FIG. 2 in accordance with embodiments describedherein;

FIG. 4 illustrates a logical flow diagram showing one embodiment of aprocess for selecting the UPF based on the determined load-regions for aplurality of UPFs and the weights generated based on the determined loadregions, which is useful in the process of FIG. 3 in accordance withembodiments described herein;

FIG. 5 illustrates a logical flow diagram showing one embodiment of aprocess for UPF load balancing using predicted throughput of new userequipment (UE) on the network based on network data analytics inaccordance with embodiments described herein;

FIG. 6 illustrates a logical flow diagram showing one embodiment of aprocess for selecting the UPF, which is useful in the process of FIG. 5in accordance with embodiments described herein;

FIG. 7 illustrates a logical flow diagram showing one embodiment of aprocess for selecting the UPF using artificial intelligence (AI) ormachine learning (ML) algorithms to perform predictive analysis ofthroughput, which is useful in the process of FIG. 6 in accordance withembodiments described herein;

FIG. 8 illustrates a logical flow diagram showing one embodiment of aprocess for UPF load balancing based on special considerations for lowlatency traffic in accordance with embodiments described herein;

FIG. 9 illustrates a logical flow diagram showing one embodiment of aprocess for selecting the UPF based on the location of the new UE andload-regions for each UPF defined by load thresholds for non-low latencytraffic, which is useful in the process of FIG. 8 in accordance withembodiments described herein;

FIG. 10 illustrates a logical flow diagram showing one embodiment of aprocess for selecting the UPF based on whether the network traffic isidentified as low latency, which is useful in the process of FIG. 9 inaccordance with embodiments described herein;

FIG. 11 illustrates a logical flow diagram showing one embodiment of aprocess for UPF load balancing supporting multiple slices, maintainingseveral load-thresholds for each UPF and each slice depending on the UPFand network slice capacity in accordance with embodiments describedherein;

FIG. 12 illustrates a logical flow diagram showing one embodiment of aprocess for selecting the network slice based on generated weights,which is useful in the process of FIG. 11 in accordance with embodimentsdescribed herein;

FIG. 13 illustrates a logical flow diagram showing one embodiment of aprocess for selecting the network slice based on determined load-regionsfor each slice and weights generated based on the determined loadregions, which is useful in the process of FIG. 12 in accordance withembodiments described herein;

FIG. 14 illustrates a logical flow diagram showing one embodiment of aprocess for UPF load balancing using predicted central processing unit(CPU) utilization and/or predicted memory utilization of new userequipment (UE) on the network based on network data analytics inaccordance with embodiments described herein;

FIG. 15 illustrates a logical flow diagram showing one embodiment of aprocess for selecting the UPF, which is useful in the process of FIG. 14in accordance with embodiments described herein;

FIG. 16 illustrates a logical flow diagram showing one embodiment of aprocess for selecting the UPF using AI or machine learning (ML)algorithms to perform predictive analysis of CPU utilization and/orpredicted memory utilization, which is useful in the process of FIG. 15in accordance with embodiments described herein;

FIG. 17 illustrates a chart showing an example of possible load-regionsthat a current load of a UPF may be determined to fall within that maybe used in the processes of FIGS. 2-7 and 15-17 in accordance withembodiments described herein.

FIG. 18 illustrates a timeline showing an example of possible UPF loadbalancing that may occur according to the processes of FIGS. 2-4 withtwo UPFs determined to fall within particular different load-regions ofthose shown in FIG. 17 at particular times in accordance withembodiments described herein;

FIG. 19 illustrates a timeline showing an example of possible UPF loadbalancing that may occur according to the processes of FIGS. 5-7 withtwo UPFs determined to fall within particular different load-regions ofthose shown in FIG. 17 at particular times in accordance withembodiments described herein.

FIG. 20 illustrates a chart showing an example of possible load-regionsfor non-low latency traffic that a current load of a UPF may bedetermined to fall within that may be used in the processes of FIGS.8-10 in accordance with embodiments described herein.

FIG. 21 shows a system diagram that describe various implementations ofcomputing systems for implementing embodiments described herein.

DETAILED DESCRIPTION

The following description, along with the accompanying drawings, setsforth certain specific details in order to provide a thoroughunderstanding of various disclosed embodiments. However, one skilled inthe relevant art will recognize that the disclosed embodiments may bepracticed in various combinations, without one or more of these specificdetails, or with other methods, components, devices, materials, etc. Inother instances, well-known structures or components that are associatedwith the environment of the present disclosure, including but notlimited to the communication systems and networks, have not been shownor described in order to avoid unnecessarily obscuring descriptions ofthe embodiments. Additionally, the various embodiments may be methods,systems, media, or devices. Accordingly, the various embodiments may beentirely hardware embodiments, entirely software embodiments, orembodiments combining software and hardware aspects.

Throughout the specification, claims, and drawings, the following termstake the meaning explicitly associated herein, unless the contextclearly dictates otherwise. The term “herein” refers to thespecification, claims, and drawings associated with the currentapplication. The phrases “in one embodiment,” “in another embodiment,”“in various embodiments,” “in some embodiments,” “in other embodiments,”and other variations thereof refer to one or more features, structures,functions, limitations, or characteristics of the present disclosure,and are not limited to the same or different embodiments unless thecontext clearly dictates otherwise. As used herein, the term “or” is aninclusive “or” operator, and is equivalent to the phrases “A or B, orboth” or “A or B or C, or any combination thereof,” and lists withadditional elements are similarly treated. The term “based on” is notexclusive and allows for being based on additional features, functions,aspects, or limitations not described, unless the context clearlydictates otherwise. In addition, throughout the specification, themeaning of “a,” “an,” and “the” include singular and plural references.

FIG. 1 illustrates a context diagram of an environment 100 in which UPFload balancing may be implemented in accordance with embodimentsdescribed herein.

UEs 110, such as cellular telephones or other Internet-of-Tings (IoT)devices use 5G wireless cellular telecommunication technology defined bystandards set by 3GPP and International Telecommunications Union (ITU)to get data connectivity between applications on the UE and DataNetworks (DNs) such as the Internet or private corporate networks.Almost all applications running on the UE, including voice, require suchdata connectivity. A Protocol Data Unit (PDU) session providesconnectivity between applications on a UE and a DN. The UE receivesservices through a PDU session, which is a logical connection betweenthe UE and DN. A DN is identified by a Data Network Name (DNN). PDUsessions can provide different types of transport services correspondingto the nature of the PDU(s) carried over the PDU session. In variousembodiments, a PDU session may be associated with a single DNN and witha single slice identified by Single-Network Slice Selection AssistanceInformation (S-NSSAI).

The UPF is one of the network functions (NFs) of the 5GC. The UPF,comprising UPF1 104 and UPF2 106 in the present example, is responsiblefor packet routing and forwarding, packet inspection, quality of service(QoS) handling, and interconnecting external PDU sessions with the DN.Although two UPFs (UPF1 104 and UPF2 106) are shown in the presentexample, additional UPFs may be utilized in various other embodiments.Each UPF (e.g., UPF1 104 and UPF2 106) is a virtual network functionresponsible for PDU sessions between the UEs 110 and the DN by anchoringthe PDU sessions of various UEs 110 on the individual UPF. The SMF 102is also one of the NFs of the 5GC and is primarily responsible forinteracting with the decoupled data plane, creating updating andremoving PDU sessions, selecting particular UPFs on which to anchor PDUsessions when new UEs appear on the network and managing session contextwith the UPF. Many of such functions are described in the 3GPP TS 23.501specification.

A network function, such as the SMF 102 and the UPF, such as UPF1 104and UPF2 106, can be implemented either as a network elements ondedicated hardware, as a software instance running on dedicatedhardware, or as a virtualized function instantiated on an appropriateplatform, e.g., a cloud infrastructure. In the present example, UPF1 104is implemented at data center 1 and UPF2 106 is implemented at datacenter 2, which is geographically separated from data center 1. The SMF102 sends messages to the UPF (comprising UPF 1 104 and UPF 2 in thepresent example) over the N4 reference interface using the PacketForwarding Control Protocol (PFCP). The PFCP may employ UDP port (8805)and is defined to support Control and User Plane Separation (CUPS).Decoupling other control plane functions from the user plane, togetherwith the 5G Core Access and Mobility Management Function (AMF) (notshown), the SMF 102 performs the role of Dynamic Host Control Protocol(DHCP) server and Internet Protocol (IP) Address Management (IPAM)system. Together with the UPF, the SMF 102 maintains a record of PDUsession state by means of a 24 bit PDU Session ID. The SMF 102 setsconfiguration parameters in the UPF that define traffic steeringparameters and ensure the appropriate routing of packets whileguaranteeing the delivery of incoming packets, though a Downlink (DL)data notification.

In the present example embodiment, each UPF1 104 and UPF2 106 may havethe ability to establish network connectivity and anchor PDU sessions ofany UE on the network via various cellular telecommunication basestations and associated antennas 108. To maximize network performance,PDU sessions are by default anchored on the UPF at the data center thatis closest geographically to the UE, as illustrated by most of thedashed lines in FIG. 1 for UEs 110 (and an operator defines a servicearea for each UPF). However, each UPF (e.g., UPF1 104 and UPF2 106) hasa maximum network capacity to handle PDU sessions anchored thereon andthe associated network traffic. Thus, PDU sessions anchored on aparticular UPF (e.g., UPF1 104) and their associated network traffic maycause the UPF to near its maximum capacity or become overloaded. UPFload balancing may then cause the PDU session of the next new UEappearing on the network (e.g., UE 112) to be anchored on a UPF at adata center (e.g., UPF2 106) that is further away than the data centerthat is closest geographically to the UE. In the present example, UPF1104 is at or near its maximum capacity with the PDU sessions of all theother UEs currently anchored on it, so UE 112 has a PDU session anchoredon UPF2 106 (as shown by dashed line 114) instead of UPF1 104, eventhough data center 2 of UPF2 106 is further away from the UE 112 thandata center 1 of UPF1 104. In various embodiments described herein,there are different particular scenarios and rules in which UPF loadbalancing may cause the PDU session of the next new UE appearing on thenetwork to be anchored on a UPF at a data center that is further awaythan the data center that is closest geographically to the UE, whichimproves overall UPF load balancing and network performance.

FIG. 2 illustrates a logical flow diagram showing one embodiment of aprocess 200 for load balancing based on current UPF load and thresholdsthat depend on UPF capacity in accordance with embodiments describedherein.

At 202, the SMF 102 maintains load thresholds for each user planefunction (UPF) of a plurality of UPFs in a cellular telecommunicationnetwork. The plurality of UPFs serve as anchor points between UE in thecellular telecommunication network and a DN. Each UPF of the pluralityof UPFs is a virtual network function responsible for interconnectingPDU sessions between the UE and the DN by anchoring the PDU sessions onindividual UPFs. The load thresholds for each UPF depend on a respectivecapacity of each UPF to have PDU sessions anchored thereon. In thepresent example embodiment, an amount of load put on a UPF by a UEappearing in the cellular telecommunication network is assumed to beidentical for all UEs appearing in the cellular telecommunicationnetwork.

At 204, the SMF 102 receives a request to anchor on a UPF a PDU sessionof a new UE newly appearing on the cellular telecommunication network.At 206, the SMF 102 selects a UPF of the plurality of UPFs on which toanchor the PDU session based on a location of the new UE and determinedload-regions for each UPF of the plurality of UPFs defined by the loadthresholds.

At 208, the SMF 102 anchors the PDU session of the new UE to theselected UPF.

FIG. 3 illustrates a logical flow diagram showing one embodiment of aprocess 300 for selecting the UPF based on generated weights, which isuseful in the process 200 of FIG. 2 in accordance with embodimentsdescribed herein.

At 302, the SMF 102 generates weights for selecting the UPF based on thedetermined load-regions.

At 304, the SMF 102 selects the UPF based on the generated weights.

FIG. 4 illustrates a logical flow diagram showing one embodiment of aprocess 400 for selecting the UPF based on the determined load-regionsfor a plurality of UPFs and the weights generated based on thedetermined load regions, which is useful in the process 300 of FIG. 3 inaccordance with embodiments described herein.

At 402, the SMF 102 generates multiple load-regions. Each load-regioncorresponds to a different range of current load of a UPF defined by oneor more of lower and upper threshold percentages of UPF load capacity.

At 404, the SMF 102 receives the request to anchor the PDU session.

At 406, the SMF 102 determines a load region from the multipleload-regions that a current load of the UPF falls within.

At 408, the SMF 102 determines whether there are additional UPFs in theplurality of UPFs on which the PDU session may be anchored. If it isdetermined there are additional UPFs on which the PDU session may beanchored, then the process 400 proceeds back to 406 to determine a loadregion from the multiple load-regions that a current load of theadditional UPF falls within. If it is determined there are notadditional UPFs on which the PDU session may be anchored, then theprocess 400 proceeds to 410.

At 410, the SMF 102 selects a UPF of the plurality of UPFs based on thedetermined load-regions for the plurality of UPFs and the weightsgenerated based on the determined load regions.

In an example embodiment, the SMF 102 generates a lowest load-regionindicating a current UPF load less than a first threshold percentage ofUPF capacity; generates one or more intermediate non-overlappingload-regions each defined by respective lower and upper thresholdpercentages of UPF capacity and indicating a current load greater thanthe lowest load-region; and generates a highest load-region indicating acurrent UPF load greater than a second threshold percentage of UPFcapacity and greater than the intermediate non-overlapping load-regions.

In the present example embodiment, each UPF is associated with adifferent respective geographic UPF service area. Selecting the UPFbased on the generated weights and the determined load-regions for theUPFs may include determining a particular UPF has (i.e., is at a datacenter in) a respective geographic area within which the location of thenew UE falls (i.e., is at a data center that is closest geographicallyto the UE compared to data centers of other UPFs). The particular UPFmay then be selected in response to the determined load-region of theparticular UPF being a load-region indicating its current load is belowa threshold capacity.

In some embodiments, the SMF 102 determines a particular UPF has arespective geographic area within which the location of the new UEfalls. The SMF 102 determines whether the particular UPF has adetermined load region indicating its current load is in a differentload region indicating a higher current load of the particular UPF thana current load of another UPF. In response to this determination, theSMF 102 weights the selection of a UPF. In particular, the UPF selectionby the SMF for load-balancing is based on weighted scheduling of load(UEs) on the UPFs. This weighted scheduling may be credit/token-based(e.g., weighted round robin) or probability based (e.g., usingstatistical based scheduling algorithms using probability). For example,the SMF 102 may weight the selection of a UPF such that a probabilitythat the particular UPF is selected is lower than a probability ofselection of the other UPF. In some embodiments, the selection of theUPF is weighted by using credit/token-based weighted scheduling orprobability-based weighted scheduling such that the frequency ofselection of the particular UPF decreases as a difference between ahigher current load of the particular UPF and a lower current load of atleast one UPF of the plurality of UPFs increases, as indicated by theload regions determined for each UPF of the plurality of UPFs.

FIG. 5 illustrates a logical flow diagram showing one embodiment of aprocess 500 for UPF load balancing using predicted throughput of a newUE on the network based on network data analytics in accordance withembodiments described herein.

At 502, the SMF 102 maintains load thresholds for each user planefunction (UPF) of a plurality of UPFs in a cellular telecommunicationnetwork. The plurality of UPFs serve as anchor points between UE in thecellular telecommunication network and a DN. Each UPF of the pluralityof UPFs is a virtual network function responsible for interconnectingPDU sessions between the UE and the DN by anchoring the PDU sessions onindividual UPFs. The load thresholds for each UPF depend on a respectivecapacity of each UPF to have PDU sessions anchored thereon. However, inthe present example embodiment, an amount of load put on a UPF by a UEappearing in the cellular telecommunication network is not assumed to beidentical for all UEs appearing in the cellular telecommunicationnetwork.

At 504, the SMF 102 receives a request to anchor on a UPF a PDU sessionof a new UE newly appearing on the cellular telecommunication network.

At 506, the SMF 102 selects a UPF of the plurality of UPFs on which toanchor the PDU session based on a location of the new UE, determinedload-regions for each UPF of the plurality of UPFs defined by the loadthresholds and predicted throughput of the new UE based on network dataanalytics. In an example embodiment, the network data analytics isprovided via a network data analytics function (NWDAF) of a 5G mobilenetwork of which the cellular telecommunication network is comprised.

At 508, the SMF 102 anchors the PDU session of the new UE to theselected UPF.

FIG. 6 illustrates a logical flow diagram showing one embodiment of aprocess 600 for selecting the UPF, which is useful in the process 500 ofFIG. 5 in accordance with embodiments described herein.

At 602, in selecting the UPF, the SMF 102 uses the network dataanalytics to predict throughput of the UE and load on a UPF of the newUE appearing on the cellular telecommunication network based on thepredicted throughput.

At 604, the SMF 102 selects a UPF of the plurality of UPFs on which toanchor the PDU session based on a location of the new UE, load-regionsfor each UPF of the plurality of UPFs defined by the load thresholds andthe predicted load of the new UE on a UPF.

FIG. 7 illustrates a logical flow diagram showing one embodiment of aprocess 700 for selecting the UPF using artificial intelligence (AI) ormachine learning (ML) algorithms to perform predictive analysis ofthroughput, which is useful in the process 600 of FIG. 6 in accordancewith embodiments described herein.

At 702, in using the network data analytics to predict throughput of thenew UE and load on a UPF, the SMF 102 uses artificial intelligence (AI)or machine learning (ML) algorithms to perform predictive analysis ofthroughput of the new UE and resulting load on a UPF of the new UEappearing on the cellular telecommunication network based on historicalactivity of the new UE appearing on the cellular telecommunicationnetwork.

At 704, the SMF 102 implements a weighted scheduling of load on UPFs toachieve UPF load-balancing based on the predicted throughput of the newUE and resulting predicted load on a UPF of the new UE. This weightedscheduling can be implemented using credit/token based schedulingalgorithms or statistical based scheduling algorithms (usingprobability). The SMF 102 may weight selection of a particular UPF ofthe plurality of UPFs based on the predicted throughput of the new UEand resulting predicted load on a UPF of the new UE by usingcredit/token-based weighted scheduling or probability-based weightedscheduling. For example, in one embodiment, the SMF 102 changes aprobability of whether a particular UPF of the plurality of UPFs will beselected based on the predicted throughput of the new UE and resultingpredicted load on a UPF of the new UE. In an example embodiment, the SMF102 weights selection of the particular UPF to not overload other UPFsof the plurality of UPFs as compared to the particular UPF in responseto a current load of the particular UPF being currently in a particularload-region as compared to other UPFs of the plurality of UPFs and thepredicted load being at a particular level. For example, the SMF 102 mayincrease a probability that a particular UPF will be selected inresponse to a current load of the particular UPF being currently in aparticular load-region as compared to other UPFs and the predicted loadbeing at a particular level. In an example embodiment, the SMF 102 mayweight selection of the particular UPF in the plurality of UPFs to notoverload the particular UPF beyond a threshold amount compared to otherUPFs in the plurality of UPFs based on the predicted load by usingcredit/token-based weighted scheduling or probability-based weightedscheduling based on the predicted load. For example, the SMF 102 maydecrease a probability that the particular UPF will be overloaded beyonda threshold amount compared to other UPFs based on the predicted load bychanging the probability of whether the particular UPF will be selectedbased on the predicted load Such load balancing may instead be achievedusing credit/token based scheduling (e.g., weighted round robin).

FIG. 8 illustrates a logical flow diagram showing one embodiment of aprocess 800 for UPF load balancing based on special considerations forlow latency traffic in accordance with embodiments described herein.

At 802, the SMF 102 maintains load thresholds for each user planefunction (UPF) of a plurality of UPFs in a cellular telecommunicationnetwork. The plurality of UPFs serve as anchor points between UE in thecellular telecommunication network and a DN. Each UPF of the pluralityof UPFs is a virtual network function responsible for interconnectingPDU sessions between the UE and the DN by anchoring the PDU sessions onindividual UPFs. The load thresholds for each UPF depend on a respectivecapacity of each UPF to have PDU sessions anchored thereon. In thepresent example embodiment, an amount of load put on a UPF by a UEappearing in the cellular telecommunication network is assumed to beidentical for all UEs appearing in the cellular telecommunicationnetwork.

In some embodiments, the load thresholds may be reduced by a percentageamount of capacity dedicated for low-latency network traffic. Forexample, a percentage amount of capacity dedicated for low-latencynetwork traffic may be 10% and thus the load thresholds for non-lowlatency traffic (such as the thresholds maintained in the process 200 ofFIG. 2 ) may be reduced by 10%.

At 804, the SMF 102 receives a request to anchor on a UPF a PDU sessionof a new UE newly appearing on the cellular telecommunication network.

At 806, the SMF 102 selects a UPF of the plurality of UPFs on which toanchor the PDU session based on whether traffic of the PDU session isidentified as low latency and a location of the new UE.

At 808, the SMF 102 anchors the PDU session of the new UE to theselected UPF.

FIG. 9 illustrates a logical flow diagram showing one embodiment of aprocess 900 for selecting the UPF based on the location of the new UEand load-regions for each UPF defined by load thresholds for non-lowlatency traffic, which is useful in the process 800 of FIG. 8 inaccordance with embodiments described herein.

At 902, the SMF 102 receives a request to anchor on a UPF a PDU sessionof a new UE newly appearing on the cellular telecommunication network.

At 904, the SMF 102 determines whether the traffic of the PDU session isidentified as low latency. In the present example embodiment, theselection of the UPF is based on dedicating a percentage of capacity ofeach UPF of the plurality of UPFs to low-latency traffic of PDUsessions. Latency may be measured in the time elapsed from when theclient sends the first byte of a request to the moment the serverreceives it, or it may be measured by the total journey time for apacket to travel to the server and then back to the client. In thepresent example, on the downlink, the latency is measured from the timethat the UPF receives the packet until the time that the packet isdelivered to the UE. On the uplink, the latency is measured from thetime that the UE sends the packet until the time that the packet isreceived by the UPF. For example, low latency network traffic maysupport operations that require near real-time access to rapidlychanging data. Low latency is desirable in a wide range of use cases. Ina general sense, lower latency is nearly always an improvement overslower packet transport. Low latency is desirable in online gaming as itcontributes to a more realistic gaming environment. The term low latencyis often used to describe specific business use cases, in particularhigh-frequency trading in capital markets. If traffic of the PDU sessionis identified as low latency, then the process 900 proceeds to 906. Iftraffic of the PDU session is not identified as low latency, then theprocess 900 proceeds to 908.

At 906, the SMF 102 selects a UPF having a closest associated locationto a current location of the new UE.

At 908, the SMF selects a UPF based on the location of the new UE andload-regions for each UPF of the plurality of UPFs defined by the loadthresholds for non-low latency traffic.

FIG. 10 illustrates a logical flow diagram showing one embodiment of aprocess 1000 for selecting the UPF based on whether the network trafficis identified as low latency, which is useful in the process 900 of FIG.9 in accordance with embodiments described herein.

At 1002, the SMF 102 receives a request to anchor on a UPF a PDU sessionof a new UE newly appearing on the cellular telecommunication network.At 1004, the SMF 102 determines whether the traffic of the PDU sessionis identified as low latency. If traffic of the PDU session isidentified as low latency, then the process 1000 proceeds to 1006. Iftraffic of the PDU session is not identified as low latency, then theprocess 1000 proceeds to 1008.

At 1006, the SMF 102 selects a UPF having a closest associated locationto a current location of the new UE.

At 1008, the SMF 102 selects a UPF based on weights for selecting theUPF generated based on the load-regions, wherein each load-regioncorresponds to a different range of current load of the UPF defined byone or more of lower and upper threshold percentages of load capacity ofthe UPF.

In some embodiments, if each UPF of the plurality of UPFs is identifiedas currently having a current load falling within a low load-regiondefined by a current load below a particular threshold, then the SMF 102selects a UPF having a closest associated location to a current locationof the new UE.

FIG. 11 illustrates a logical flow diagram showing one embodiment of aprocess 1100 for UPF load balancing supporting multiple slices,maintaining several load-thresholds for each UPF and each slicedepending on the UPF and network slice capacity in accordance withembodiments described herein.

At 1102, the SMF 102 maintains load thresholds for each network slice ofa plurality of network slices. In the present example embodiment, eachnetwork slice of each respective set of network slices comprises of aset of virtual network resources and network traffic flows associatedwith the network slice and represents an independent virtualizedinstance of a network defined by allocation of a subset of availablenetwork resources in the cellular telecommunication network. Eachnetwork slice of the plurality of network slices is supported by arespective user plane function (UPF) of a plurality of UPFs in acellular telecommunication network. The plurality of UPFs serve asanchor points between user equipment (UE) in the cellulartelecommunication network and a data network (DN). Each UPF of theplurality of UPFs is a virtual network function responsible forinterconnecting packet data unit (PDU) sessions between the userequipment (UE) and the DN by anchoring the PDU sessions on individualUPFs. The load thresholds for each network slice depend on a respectivecapacity of each network slice and total capacity of each UPF supportingeach network slice to have PDU sessions anchored thereon. An amount ofload put on a network slice by a UE appearing in the cellulartelecommunication network is assumed to be identical for all UEsappearing in the cellular telecommunication network.

At 1104, the SMF 102 receives a request to anchor on a UPF a PDU sessionof a new UE newly appearing on the cellular telecommunication network.

At 1106, the SMF 102 selects a network slice of the plurality of networkslices on which to anchor the PDU session based on a location of the newUE and determined load-regions for each network slice of the pluralityof network slices defined by the load thresholds.

At 1108, the SMF 102 anchors the PDU session of the new UE to theselected network slice and the respective UPF supporting the selectednetwork slice.

FIG. 12 illustrates a logical flow diagram showing one embodiment of aprocess 1200 for selecting the network slice based on generated weights,which is useful in the process 1100 of FIG. 11 in accordance withembodiments described herein.

At 1202, the SMF 102 generates weights for selecting the network slicebased on the determined load-regions.

At 1204, the SMF 102 selects the network slice based on the generatedweights.

FIG. 13 illustrates a logical flow diagram showing one embodiment of aprocess 1300 for selecting the network slice based on determinedload-regions for each slice and weights generated based on thedetermined load regions, which is useful in the process 1200 of FIG. 12in accordance with embodiments described herein.

At 1302, the SMF 102 generates multiple load-regions. Each load-regioncorresponds to a different range of current load of a network slicedefined by one or more of lower and upper threshold percentages ofnetwork slice load capacity. For example, in one embodiment, the SMF 102may generate a lowest load-region indicating a current network sliceload less than a first threshold percentage of network slice capacity;generate one or more intermediate non-overlapping load-regions eachdefined by respective lower and upper threshold percentages of networkslice capacity and indicating a current load greater than the lowestload-region; and generate a highest load-region indicating a currentnetwork slice load greater than a second threshold percentage of networkslice capacity and greater than the intermediate load-region(s).

At 1304, the SMF 102 receives the request to anchor the PDU session.

At 1306, the SMF 102, in response to receiving the request to anchor thePDU session, determines a load region from the multiple load-regionsthat a current load of a network slice falls within.

At 1306, the SMF 102 determines whether there are any additional networkslides on which the PDU session may be anchored. If it is determinedthere are additional network slides on which the PDU session may beanchored, then process 1300 proceeds back to 1306 to determine a loadregion from the multiple load-regions that a current load of theadditional network slice falls within. If it is determined there are notadditional network slides on which the PDU session may be anchored, thenthe process 1300 proceeds to 1310.

At 1310, the SMF 102 selects a network slice of the plurality of networkslices based on the determined load-regions for the plurality of networkslices and the weights generated based on the determined load regions.In some embodiments, each network slice of the plurality of networkslices is associated with a respective geographic area of the respectiveUPF supporting the network slice (i.e., the geographic area of the datacenter of the UPF). Selecting a network slice based on the generatedweights and the determined load-regions for the plurality of networkslices may include determining a particular network slice of theplurality of network slices is associated with a respective geographicarea within which the location of the new UE falls. The SMF 102 may thenselect the particular network slice in response the determinedload-region of the particular network slice being a load-regionindicating a current load of the particular network slice is below athreshold capacity.

In some embodiments, selecting a network slice based on the generatedweights and the determined load-regions for the plurality of networkslices may include determining whether the particular network slice hasa determined load region indicating a current load of the particularnetwork slice is in a different load region indicating a higher currentload of the particular network slice than a current load of anothernetwork slice. In response to this, the SMF 102 may weight the selectionof a network slice of the plurality of network slices such that theparticular network slice is not overloaded compared to the other networkslice by using credit/token-based weighted scheduling orprobability-based weighted scheduling.

In some embodiments, the selection of a network slice includesdetermining a particular network slice of the plurality of networkslices is associated with a respective geographic area within which thelocation of the new UE falls. The selection of the network slice is thenweighted by using credit/token-based weighted scheduling orprobability-based weighted scheduling such that the frequency ofselection of the particular network slice decreases as a differencebetween a higher current load of the particular network slice and alower current load of at least one network slice of the plurality ofnetwork slices increases, as indicated by the load regions determinedfor each network slice of the plurality of network slices.

FIG. 14 illustrates a logical flow diagram showing one embodiment of aprocess 1400 for UPF load balancing using predicted CPU utilizationand/or predicted memory utilization of new UE on the network based onnetwork data analytics in accordance with embodiments described herein.

At 1402, the SMF 102 maintains load thresholds for each UPF of aplurality of UPFs in a cellular telecommunication network. The pluralityof UPFs serve as anchor points between UE in the cellulartelecommunication network and a DN. Each UPF of the plurality of UPFs isa virtual network function responsible for interconnecting PDU sessionsbetween the UE and the DN by anchoring the PDU sessions on individualUPFs. The load thresholds for each UPF depend on a respective capacityof each UPF to have PDU sessions anchored thereon.

At 1404, the SMF 102 receives a request to anchor on a UPF a PDU sessionof a new UE newly appearing on the cellular telecommunication network.

At 1406, the SMF 102 selects a UPF of the plurality of UPFs on which toanchor the PDU session based on a location of the new UE, load-regionsfor each UPF of the plurality of UPFs defined by the load thresholds andone or more of predicted CPU utilization and predicted memoryutilization of the new UE based on network data analytics. In someembodiments, the network data analytics may be provided via an NWDAF ofa 5G mobile network of which the cellular telecommunication network iscomprised.

FIG. 15 illustrates a logical flow diagram showing one embodiment of aprocess 1500 for selecting the UPF, which is useful in the process 1400of FIG. 14 in accordance with embodiments described herein.

At 1502, the SMF 102 uses the network data analytics to predict one ormore of CPU utilization and memory utilization of the UE and load on aUPF of the new UE appearing on the cellular telecommunication networkbased on one or more of the predicted CPU utilization and predictedmemory utilization.

At 1504, the SMF 102 selects a UPF of the plurality of UPFs on which toanchor the PDU session based on a location of the new UE, load-regionsfor each UPF of the plurality of UPFs defined by the load thresholds andthe predicted load of the new UE on a UPF.

FIG. 16 illustrates a logical flow diagram showing one embodiment of aprocess for 1600 selecting the UPF using AI or machine learning MLalgorithms to perform predictive analysis of CPU utilization and/orpredicted memory utilization, which is useful in the process 1500 ofFIG. 15 in accordance with embodiments described herein.

At 1602, the SMF 102 uses artificial intelligence (AI) or machinelearning (ML) algorithms to perform predictive analysis of one or moreof CPU utilization and memory utilization of the new UE and resultingload on a UPF of the new UE appearing on the cellular telecommunicationnetwork based on historical activity of the new UE appearing on thecellular telecommunication network.

At 1604, the SMF 102 implements a weighted scheduling of load on UPFs toachieve UPF load-balancing based on one or more of the predicted CPUutilization and predicted memory utilization of the new UE and resultingpredicted load on a UPF of the new UE. This weighted scheduling can beimplemented using credit/token based scheduling algorithms orstatistical based scheduling algorithms (using probability). The SMF 102may weight selection of the a particular UPF to not overload other UPFsof the plurality of UPFs as compared to the particular UPF in responseto a current load of the particular UPF being currently in a particularload-region as compared to other UPFs of the plurality of UPFs and theresulting predicted load resulting from one or more of the predicted CPUutilization and predicted memory utilization being at a particularlevel. For example, in one embodiment, the SMF 102 may increase aprobability that a particular UPF will be selected in response to acurrent load of the particular UPF being currently in a particularload-region as compared to other UPFs of the plurality of UPFs and theresulting predicted load resulting from one or more of the predicted CPUutilization and predicted memory utilization being at a particularlevel. The SMF 102 may weight selection of the particular UPF in theplurality of UPFs to not overload the particular UPF beyond a thresholdamount compared to other UPFs in the plurality of UPFs based on theresulting predicted load by using credit/token-based weighted schedulingor probability-based weighted scheduling based on the resultingpredicted load resulting from one or more of the predicted CPUutilization and predicted memory utilization. For example, the SMF 102may decrease a probability that the particular UPF in the plurality ofUPFs will be overloaded beyond a threshold amount compared to other UPFsin the plurality of UPFs based on the resulting predicted load bychanging the probability of whether the particular UPF will be selectedbased on the resulting predicted load resulting from one or more of thepredicted CPU utilization and predicted memory utilization. Such loadbalancing may instead be achieved using credit/token based scheduling(e.g., weighted round robin).

FIG. 17 illustrates a chart 1700 showing an example of possibleload-regions that a current load of a UPF may be determined to fallwithin that may be used in the processes of FIGS. 2-7 and 15-17 inaccordance with embodiments described herein.

The chart 1700 indicates the load region 1702 and the range ofpercentage of total load capacity 1704 for each load-region 1702 definedby respective load thresholds indicated in the chart 1700. In thepresent example, the “Low” load region indicates a current UPF load ofless than 30% of the total load capacity. The “Medium” load regionindicates a current UPF load of greater than or equal to 30% and lessthan 55% of the total load capacity. The “High” load region indicates acurrent UPF load of greater than or equal to 55% and less than 75% ofthe total load capacity. The “Very High” load region indicates a currentUPF load of greater than or equal to 75% of the total load capacity.There may be additional or different load regions in various otherembodiments. The chart 1700 may be stored or represented as a datastructure in computer memory and may be maintained and/or accessible bythe SMF 102.

FIG. 18 illustrates a timeline 1800 showing an example of possible UPFload balancing that may occur according to the processes of FIGS. 2-4with two UPFs determined to fall within particular differentload-regions of those shown in the chart 1700 FIG. 17 at particulartimes in accordance with embodiments described herein.

For each example point in time t=1, t=2, t=3 and t=4, shown in thetimeline 1800 is the determined UPF1 load 1802, the determined UPF2 load1806 and the corresponding UPF1 load balancing action 1804 and UPF2 loadbalancing action 1808.

Referring now also to FIG. 1 , in the present example, at time t=1, theSMF 102 determines that the current load of UPF1 104 is 20% of the totalload capacity for UPF1 104 and thus determines the load region or UPF1104 is “low” based on the load thresholds in the chart 1700 of FIG. 17 .At time t=1, the SMF 102 also determines that the current load of UPF2106 is 2% of the total load capacity for UPF2 106 and thus determinesthe load region or UPF2 106 is also “low” based on the load thresholdsin the chart 1700 of FIG. 17 . Based on the determined load regions forUPF1 104 and UPF2 106, any new UE in the region of UPF1 104 (e.g., theregion of UPF1 104 being a respective geographic area associated withdata center 1) are anchored on UPF1 104 and any new UE in the region ofUPF2 106 (e.g., the region of UPF2 106 being a respective geographicarea associated with data center 2) are anchored on UPF2 106.

At time t=2, the SMF 102 determines that the current load of UPF1 104 is45% of the total load capacity for UPF1 104 and thus determines the loadregion or UPF1 104 is “medium” based on the load thresholds in the chart1700 of FIG. 17 . At time t=2, the SMF 102 also determines that thecurrent load of UPF2 106 is 10% of the total load capacity for UPF2 106and thus determines the load region or UPF2 106 is “low” based on theload thresholds in the chart 1700 of FIG. 17 . Based on the determinedload regions for UPF1 104 and UPF2 106, the weights determined by theSMF 102 for UPF1 104 load balancing are 1 & 2. In particular, for everythree new UEs in the region of UPF1 104 (data center 1), one is anchoredon UPF1 104 and the other two are anchored on UPF2 106. In variousembodiments, the load balancing can be done using credit/token basedscheduling algorithms (using weighted round robin) or done randomly(using statistical based scheduling algorithms using probability): withprobability ⅓ a new UE is anchored on UPF1 104 and with probability ⅔the new UE is anchored on UPF2 106. Any new UE in the region of UPF2 106are anchored on UPF2 106 (data center 2).

At time t=3, the SMF 102 determines that the current load of UPF1 104 is65% of the total load capacity for UPF1 104 and thus determines the loadregion or UPF1 104 is “high” based on the load thresholds in the chart1700 of FIG. 17 . At time t=3, the SMF 102 also determines that thecurrent load of UPF2 106 is 19% of the total load capacity for UPF2 106and thus determines the load region or UPF2 106 is “low” based on theload thresholds in the chart 1700 of FIG. 17 . Based on the determinedload regions for UPF1 104 and UPF2 106, the weights determined by theSMF 102 for UPF1 104 load balancing are 1 & 4. In particular for everyfive new UEs in the region of UPF1 (data center1), one is anchored onUPF1 and the other four are anchored on UPF2. In various embodiments,the load balancing can be done by the SMF 102 using weighted round robinor done randomly, with probability ⅕ a new UE is anchored on UPF1 andwith probability ⅘ the new UE is anchored on UPF2). Any new UE in theregion of UPF2 106 (e.g., the region of UPF2 106 being a respectivegeographic area associated with data center 2) are anchored on UPF2 106(data center 2).

At time t=4, the SMF 102 determines that the current load of UPF1 104 is75% of the total load capacity for UPF1 104 and thus determines the loadregion or UPF1 104 is “very high” based on the load thresholds in thechart 1700 of FIG. 17 . At time t=4, the SMF 102 also determines thatthe current load of UPF2 106 is 25% of the total load capacity for UPF2106 and thus determines the load region or UPF2 106 is “low” based onthe load thresholds in the chart 1700 of FIG. 17 . Based on thedetermined load regions for UPF1 104 and UPF2 106, any new UE in theregion of UPF1 104 (data center 1) are anchored on UPF2 106 and any newUE in the region of UPF2 106 (data center 2) are also anchored on UPF2106. In some embodiments, the credit based scheduling method, such asthe weighted round robin scheduling, disclosed herein is based on aprobabilistic model. Alternatively, a credit/token based weighted roundrobin scheduling can be used in various other embodiments.

FIG. 19 illustrates a timeline showing an example of possible UPF loadbalancing that may occur according to the processes of FIGS. 5-7 withtwo UPFs determined to fall within particular different load-regions ofthose shown in FIG. 17 at particular times in accordance withembodiments described herein.

For each example point in time t=1, t=2, t=3 and t=4, shown in thetimeline 1900 is the determined UPF1 load 1902, the determined UPF2 load1906, the corresponding UPF1 load balancing action 1904 and UPF2 loadbalancing action 1908, as well as example new UE predicted loads 1910.For example, the predicted load may be based on data from the networkdata analytics function (NWDAF). The predicted load may be measured inunits based on throughput (e.g., packets per second, bytes per second,and/or bits per second), CPU utilization (e.g., CPU clock cycles, clockticks, CPU time, CPU time per second, process time, percentage of CPUcapacity utilization) and/or memory utilization, (megabytes of memory,and/or percentage of memory capacity utilization) or any combinationthereof.

Referring now also to FIG. 1 , in the present example, at time t=1, theSMF 102 determines that the current load of UPF1 104 is 20% of the totalload capacity for UPF1 104 and thus determines the load region or UPF1104 is “low” based on the load thresholds in the chart 1700 of FIG. 17 .At time t=1, the SMF 102 also determines that the current load of UPF2106 is 2% of the total load capacity for UPF2 106 and thus determinesthe load region or UPF2 106 is also “low” based on the load thresholdsin the chart 1700 of FIG. 17 . In this case, based on the determinedload regions for UPF1 104 and UPF2 106, regardless of any predicted loadof the new UE, any new UE in the region of UPF1 104 (data center 1) areanchored on UPF1 104 and any new UE in the region of UPF2 106 (datacenter 2) are anchored on UPF2 106.

At time t=2, the SMF 102 determines that the current load of UPF1 104 is45% of the total load capacity for UPF1 104 and thus determines the loadregion or UPF1 104 is “medium” based on the load thresholds in the chart1700 of FIG. 17 . At time t=2, the SMF 102 also determines that thecurrent load of UPF2 106 is 10% of the total load capacity for UPF2 106,and thus determines the load region or UPF2 106 is “low” based on theload thresholds in the chart 1700 of FIG. 17 . Based on the determinedload regions for UPF1 104 and UPF2 106, the weights determined by theSMF 102 for UPF1 104 load balancing are 1 & 2. For example, based on thedetected predicted load of the new UE appearing on the network, if theSMF 102 determines that the predicted load of the new UE is 2 units ofload, the SMF 102 will perform load balancing such that there is a 43%probability the SMF 102 anchors the UE to UPF1 104 and a 57% probabilitythe SMF 102 anchors the UE to UPF2 106. If the SMF 102 determines thatthe predicted load of the new UE is 1 unit of load, the SMF 102 willperform load balancing such that there is a 25% probability the SMF 102anchors the UE to UPF1 104 and a 75% probability the SMF 102 anchors theUE to UPF2 106. Any new UE in the region of UPF2 (data center 2) 106 areanchored on UPF2 106.

At time t=3, the SMF 102 determines that the current load of UPF1 104 is65% of the total load capacity for UPF1 104 and thus determines the loadregion or UPF1 104 is “high” based on the load thresholds in the chart1700 of FIG. 17 . At time t=3, the SMF 102 also determines that thecurrent load of UPF2 106 is 19% of the total load capacity for UPF2 106and thus determines the load region or UPF2 106 is “low” based on theload thresholds in the chart 1700 of FIG. 17 . Based on the determinedload regions for UPF1 104 and UPF2 106, the weights determined by theSMF 102 for UPF1 104 load balancing are 1 & 4. For example, based on thedetected predicted load of the new UE appearing on the network, if theSMF 102 determines that the predicted load of the new UE is 2 units ofload, the SMF 102 will perform load balancing such that there is a 10%probability the SMF 102 anchors the UE to UPF1 104 and a 90% probabilitythe SMF 102 anchors the UE to UPF2 106. If the SMF 102 determines thatthe predicted load of the new UE is 1 unit of load, the SMF 102 willperform load balancing such that there is a 28.6% probability the SMF102 anchors the UE to UPF1 104 and a 71.4% probability the SMF 102anchors the UE to UPF2 106. Any new UE in the region of UPF2 106 (datacenter 2) are anchored on UPF2 106.

At time t=4, the SMF 102 determines that the current load of UPF1 104 is75% of the total load capacity for UPF1 104 and thus determines the loadregion or UPF1 104 is “very high” based on the load thresholds in thechart 1700 of FIG. 17 . At time t=4, the SMF 102 also determines thatthe current load of UPF2 106 is 25% of the total load capacity for UPF2106 and thus determines the load region or UPF2 106 is “low” based onthe load thresholds in the chart 1700 of FIG. 17 . In this case, basedon the determined load regions for UPF1 104 and UPF2 106, regardless ofany predicted load of the new UE, any new UE in the region of UPF1 104(data center 1) are anchored on UPF2 106 and any new UE in the region ofUPF2 106 (data center 2) are also anchored on UPF2 106.

FIG. 20 illustrates a chart 2000 showing an example of possibleload-regions for non-low latency traffic that a current load of a UPFmay be determined to fall within that may be used in the processes ofFIGS. 8-10 in accordance with embodiments described herein.

The chart 2000 indicates the load region 2002 and the range ofpercentage of total load capacity 2004 for each load-region 2002 definedby respective load thresholds indicated in the chart 1700. Theload-regions shown in the chart 2000 are used for UPF load balancingbased on special considerations for low latency traffic. The loadthresholds are reduced compared to those of chart 1700 in FIG. 17 by apercentage amount of capacity dedicated for low-latency network traffic.In the present example, the percentage amount of capacity dedicated forlow-latency network traffic is 10% and thus the load thresholds fornon-low latency traffic are reduced by 10%. In particular, “Low” loadregion indicates a current UPF load of less than 20% of the total loadcapacity. The “Medium” load region indicates a current UPF load ofgreater than or equal to 20% and less than 45% of the total loadcapacity. The “High” load region indicates a current UPF load of greaterthan or equal to 45% and less than 65% of the total load capacity. The“Very High” load region indicates a current UPF load of greater than orequal to 65% of the total load capacity. There may be additional ordifferent load regions in various other embodiments. The chart 1700 maybe stored or represented as a data structure in computer memory and maybe maintained and/or accessible by the SMF 102.

In one embodiment, in performing UPF load balancing based on specialconsiderations for low latency traffic, the SMF 102 may perform suchload balancing in the manner described with respect to the processes ofFIGS. 8-10 and the example herein described with respect to FIGS. 18 ,but uses the non-low latency load thresholds in chart 1700 instead thatare reduced to dedicate 10% of the total load capacity for low-latencynetwork traffic.

Also, a chart and/or corresponding data structure similar to that ofFIG. 17 using load thresholds shown therein may be generated or used bythe SMF 102 to perform UPF load balancing supporting multiple slices asdescribed herein with respect to the processes of FIGS. 11-13 . In suchan embodiment, the chart and/or corresponding data structure also orinstead indicates such load-thresholds for each slice depending on theUPF and network slice capacity. For example, these load thresholds maybe percentage based, such as 30%, 55%, and 75% for slice 1 and 30%, 45%,and 65% for slice 2. Also, depending on the UPFs slice basedload-regions, the SMF 102 creates slice based weights for a weightedload balancing between slices of different UPFs. The SMF 102 maintainsthe load-regions of the UPFs and creates the slice weights for theweighted load balancing of the UEs/PDU sessions among the UPFs. In suchan embodiment, depending on the UPFs slice loads, the SMF 102 createsslice weights for a weighted load balancing of the UEs/PDU sessionsamong the UPFs.

In various embodiments, there may be additional UPFs and additionalcorresponding data centers. Additional load regions may be determinedfor each UPF, and the weighting and load balancing may be performed, inone example embodiment as described herein, to adjust the probabilitiesthat a new UE appearing in the network is anchored on a particular UPFbased on determined load regions for each UPF and the location of theUE. Such load balancing may instead be achieved using credit/token basedscheduling (e.g., weighted round robin).

FIG. 21 shows a system diagram that describe various implementations ofcomputing systems 2100 for implementing embodiments described herein.

The SMF 102 and the UPF, such as UPF1 104 and UPF2 106, can beimplemented either as a network elements on dedicated hardware, as asoftware instance running on dedicated hardware, or as a virtualizedfunction instantiated on an appropriate platform, e.g., a cloudinfrastructure. In some embodiments, such NFs may be completelysoftware-based and designed as cloud-native, meaning that they'reagnostic to the underlying cloud infrastructure, allowing higherdeployment agility and flexibility. However, FIG. 21 illustrates anexample of underlying hardware on which the SMF 102 and the UPF, such asUPF1 104 and UPF2 106, may be implemented. For example, SMF 102 may beimplemented using SMF computer system(s) 2101. In some embodiments, oneor more special-purpose computing systems may be used to implement SMF102. Accordingly, various embodiments described herein may beimplemented in software, hardware, firmware, or in some combinationthereof. SMF computer system(s) 2101 may include memory 2102, one ormore central processing units (CPUs) 2114, I/O interfaces 2118, othercomputer-readable media 2120, and network connections 2122.

Memory 2102 may include one or more various types of non-volatile and/orvolatile storage technologies. Examples of memory 2102 may include, butare not limited to, flash memory, hard disk drives, optical drives,solid-state drives, various types of random access memory (RAM), varioustypes of read-only memory (ROM), other computer-readable storage media(also referred to as processor-readable storage media), or the like, orany combination thereof. Memory 2102 may be utilized to storeinformation, including computer-readable instructions that are utilizedby CPU 2114 to perform actions, including embodiments described herein.

Memory 2102 may have stored thereon SMF module 2104. The SMF module 2104is configured to implement and/or perform some or all of the functionsof the SMF 102 described herein. Memory 2102 may also store otherprograms and data 2110, which may include load thresholds, load-regions,databases, load-balancing rules, AI or ML programs to perform predictiveanalysis of UPF load based on predicted UE throughput, CPU utilizationand/or memory utilization using data from the NWDAF, user interfaces,operating systems, other network management functions, other NFs, etc.

Network connections 2122 are configured to communicate with othercomputing devices to facilitate the load balancing described herein. Invarious embodiments, the network connections 2122 include transmittersand receivers (not illustrated) to send and receive data as describedherein, such as sending data to and receiving data from UPFs, UEs andother NFs to send and receive instructions, commands and data toimplement the processes described herein. I/O interfaces 2118 mayinclude a video interfaces, other data input or output interfaces, orthe like. Other computer-readable media 2120 may include other types ofstationary or removable computer-readable media, such as removable flashdrives, external hard drives, or the like.

In some embodiments, one or more special-purpose computing systems maybe used to implement UPF, such as UPF1 104 and UPF2 106. Accordingly,various embodiments described herein may be implemented in software,hardware, firmware, or in some combination thereof. UPF computersystem(s) 2112 is an example of a computer system that may implement aUPF, such as UPF1 104 and UPF2 106. For example, computer system(s) 2112may be present in data center 1 to implement UPF1 104 or present in datacenter 2 to implement UPF2 106. Computer system(s) 2112 may includememory 2130, one or more central processing units (CPUs) 2144, I/Ointerfaces 2148, other computer-readable media 2150, and networkconnections 2152.

Memory 2130 may include one or more various types of non-volatile and/orvolatile storage technologies similar to memory 2102. Memory 2130 may beutilized to store information, including computer-readable instructionsthat are utilized by CPU 2144 to perform actions, including embodimentsdescribed herein.

Memory 2130 may have stored thereon UPF module 2124. The UPF module 214receives the messages or instructions from the SMF module 204 to performthe load balancing operations as described herein. Memory 2130 may alsostore other programs and data 2138, which may include load thresholds,load-regions, databases, load-balancing rules, AI or ML programs toperform predictive analysis of UPF load based on predicted UEthroughput, CPU utilization and/or memory utilization using data fromthe NWDAF, user interfaces, operating systems, other network managementfunctions, other NFs, etc.

Network connections 2152 are configured to communicate with othercomputing devices, such as SMF computer system(s) 2101. In variousembodiments, the network connections 2152 include transmitters andreceivers (not illustrated) to send and receive data as describedherein. I/O interfaces 2148 may include one or more other data input oroutput interfaces. Other computer-readable media 2150 may include othertypes of stationary or removable computer-readable media, such asremovable flash drives, external hard drives, or the like.

The various embodiments described above can be combined to providefurther embodiments. These and other changes can be made to theembodiments in light of the above-detailed description. In general, inthe following claims, the terms used should not be construed to limitthe claims to the specific embodiments disclosed in the specificationand the claims, but should be construed to include all possibleembodiments along with the full scope of equivalents to which suchclaims are entitled. Accordingly, the claims are not limited by thedisclosure.

1. A system comprising: a memory that stores computer instructions; anda processor that executes the computer instructions to perform actions,the actions including: maintaining a plurality of load thresholds foreach user plane function (UPF) of a plurality of UPFs in a cellulartelecommunication network, wherein: the plurality of UPFs serve asanchor points between user equipment (UE) in the cellulartelecommunication network and a data network (DN); each UPF of theplurality of UPFs is a virtual network function responsible forinterconnecting packet data unit (PDU) sessions between the userequipment (UE) and the DN by anchoring the PDU sessions on individualUPFs; and the plurality of load thresholds for each UPF depend on arespective capacity of each UPF to have PDU sessions anchored thereon;receiving a request to anchor on a UPF a PDU session of a new UE newlyappearing on the cellular telecommunication network; selecting a UPF ofthe plurality of UPFs on which to anchor the PDU session based on alocation of the new UE.
 2. The system of claim 1, wherein selecting aUPF of the plurality of UPFs on which to anchor the PDU session based ona location of the new UE includes: using the network data analytics topredict load on a UPF of the new UE appearing on the cellulartelecommunication network; and selecting a UPF of the plurality of UPFson which to anchor the PDU session based on a location of the new UE andthe predicted load of the new UE on a UPF.
 3. The system of claim 2,wherein the network data analytics is provided via a network dataanalytics function (NWDAF) of a 5^(th) generation (5G) mobile network ofwhich the cellular telecommunication network is comprised.
 4. The systemof claim 2, wherein the using the network data analytics to predict loadon a UPF of the new UE appearing on the cellular telecommunicationnetwork includes: using artificial intelligence (AI) or machine learning(ML) algorithms to perform predictive analysis of load on a UPF of thenew UE appearing on the cellular telecommunication network based onhistorical activity of the new UE appearing on the cellulartelecommunication network.
 5. The system of claim 2, wherein theselecting a UPF of the plurality of UPFs includes: weighting selectionof a particular UPF of the plurality of UPFs based on predicted load ona UPF of the new UE by using credit/token-based weighted scheduling orprobability-based weighted scheduling.
 6. The system of claim 5, whereinthe weighting selection of a particular UPF based on predicted load on aUPF of the new UE includes: weighting selection of the a particular UPFto not overload other UPFs of the plurality of UPFs as compared to theparticular UPF in response to a current load of the particular UPF beingcurrently in a particular load-region as compared to other UPFs of theplurality of UPFs and the predicted load being at a particular level. 7.The system of claim 5, wherein the weighting selection of whether aparticular UPF based on predicted load on a UPF of the new UE includes:weighting selection of the particular UPF in the plurality of UPFs tonot overload the particular UPF beyond a threshold amount compared toother UPFs in the plurality of UPFs based on the predicted load by usingcredit/token-based weighted scheduling or probability-based weightedscheduling based on the predicted load.
 8. A method comprising:electronically maintaining a plurality of load thresholds for each userplane function (UPF) of a plurality of UPFs in a cellulartelecommunication network, wherein: the plurality of UPFs serve asanchor points between user equipment (UE) in the cellulartelecommunication network and a data network (DN); each UPF of theplurality of UPFs is a virtual network function responsible forinterconnecting packet data unit (PDU) sessions between the userequipment (UE) and the DN by anchoring the PDU sessions on individualUPFs; and the plurality of load thresholds for each UPF depend on arespective capacity of each UPF to have PDU sessions anchored thereon;electronically receiving a request to anchor on a UPF a PDU session of anew UE newly appearing on the cellular telecommunication network;electronically selecting a UPF of the plurality of UPFs on which toanchor the PDU session based on a location of the new UE; andelectronically anchoring the PDU session of the new UE to the selectedUPF.
 9. The method of claim 8, wherein selecting a UPF of the pluralityof UPFs on which to anchor the PDU session based on a location of thenew UE includes: using the network data analytics to predict load on aUPF of the new UE appearing on the cellular telecommunication networkbased on one or more of the predicted CPU utilization and predictedmemory utilization; and selecting a UPF of the plurality of UPFs onwhich to anchor the PDU session based on a location of the new UE andthe predicted load of the new UE on a UPF.
 10. The method of claim 9,wherein the network data analytics is provided via a network dataanalytics function (NWDAF) of a 5^(th) generation (5G) mobile network ofwhich the cellular telecommunication network is comprised.
 11. Themethod of claim 9, wherein the using the network data analytics topredict one or more of CPU utilization and memory utilization of the newUE and load on a UPF of the new UE appearing on the cellulartelecommunication network includes: using artificial intelligence (AI)or machine learning (ML) algorithms to perform predictive analysis ofload on a UPF of the new UE appearing on the cellular telecommunicationnetwork based on historical activity of the new UE appearing on thecellular telecommunication network.
 12. The method of claim 9, whereinthe selecting a UPF of the plurality of UPFs includes: weightingselection of a particular UPF of the plurality of UPFs based onpredicted load on a UPF of the new UE by using credit/token-basedweighted scheduling or probability-based weighted scheduling.
 13. Themethod of claim 12, wherein the weighting selection of a particular UPFbased on predicted load on a UPF of the new UE includes: weightingselection of the a particular UPF to not overload other UPFs of theplurality of UPFs as compared to the particular UPF in response to acurrent load of the particular UPF being currently in a particularload-region as compared to other UPFs of the plurality of UPFs and thepredicted load being at a particular level.
 14. The method of claim 12,wherein the weighting selection of whether a particular UPF based onpredicted load on a UPF of the new UE includes: weighting selection ofthe particular UPF in the plurality of UPFs to not overload theparticular UPF beyond a threshold amount compared to other UPFs in theplurality of UPFs based on the predicted load by usingcredit/token-based weighted scheduling or probability-based weightedscheduling based on the predicted load.
 15. A non-transitorycomputer-readable storage medium having computer-executable instructionsstored thereon that, when executed by at least one computer processor,cause actions to be performed including: maintaining a plurality of loadthresholds for each user plane function (UPF) of a plurality of UPFs ina cellular telecommunication network, wherein: the plurality of UPFsserve as anchor points between user equipment (UE) in the cellulartelecommunication network and a data network (DN); each UPF of theplurality of UPFs is a virtual network function responsible forinterconnecting packet data unit (PDU) sessions between the userequipment (UE) and the DN by anchoring the PDU sessions on individualUPFs; and the plurality of load thresholds for each UPF depend on arespective capacity of each UPF to have PDU sessions anchored thereon;receiving a request to anchor on a UPF a PDU session of a new UE newlyappearing on the cellular telecommunication network; selecting a UPF ofthe plurality of UPFs on which to anchor the PDU session based on alocation of the new UE; and anchoring the PDU session of the new UE tothe selected UPF.
 16. The non-transitory computer-readable storagemedium of claim 15, wherein selecting a UPF of the plurality of UPFs onwhich to anchor the PDU session based on a location of the new UEincludes: using the network data analytics to predict load on a UPF ofthe new UE appearing on the cellular telecommunication network based onone or more of the predicted CPU utilization and predicted memoryutilization; and selecting a UPF of the plurality of UPFs on which toanchor the PDU session based on a location of the new UE and thepredicted load of the new UE on a UPF.
 17. The non-transitorycomputer-readable storage medium of claim 16, wherein the network dataanalytics is provided via a network data analytics function (NWDAF) of a5^(th) generation (5G) mobile network of which the cellulartelecommunication network is comprised.
 18. The non-transitorycomputer-readable storage medium of claim 16, wherein the using thenetwork data analytics to predict one or more of CPU utilization andmemory utilization of the new UE and load on a UPF of the new UEappearing on the cellular telecommunication network includes: usingartificial intelligence (AI) or machine learning (ML) algorithms toperform predictive analysis of load on a UPF of the new UE appearing onthe cellular telecommunication network based on historical activity ofthe new UE appearing on the cellular telecommunication network.
 19. Thenon-transitory computer-readable storage medium of claim 16, wherein theselecting a UPF of the plurality of UPFs includes: weighting selectionof a particular UPF of the plurality of UPFs based on predicted load ona UPF of the new UE by using credit/token-based weighted scheduling orprobability-based weighted scheduling.
 20. The non-transitorycomputer-readable storage medium of claim 19, wherein the weightingselection of a particular UPF based on predicted load on a UPF of thenew UE includes: weighting selection of the a particular UPF to notoverload other UPFs of the plurality of UPFs as compared to theparticular UPF in response to a current load of the particular UPF beingcurrently in a particular load-region as compared to other UPFs of theplurality of UPFs and the predicted load being at a particular level.